Introduction to Disciplined Agile Delivery - Second Edition by Ambler Scott; Lines Mark;

Author:Ambler, Scott; Lines, Mark;
Language: eng
Format: epub
Publisher: Project Management Institute

1 See AgileData.org.

Chapter 7

Construction Iteration C2

Iteration planning session. The team comes in Monday morning refreshed and ready to start a new iteration. Patricia walks the team through the highest priority work items that collectively add up to 16 points. For each story, she explains the functionality and the acceptance criteria. She has brought a few screen mockups to the planning session that she shares with the team. The mockups are a good start, but as they found during the first iteration, they aren't sufficient. For two of the stories, she finds that she needs to draw a flowchart to describe the business logic supporting the story. She also takes time to describe several business terms, often to respond to questions from Dick, who likes to understand these sorts of things. The other team members also find that these conversations have helped to clarify several concepts about which they were unsure.

For each story, Ashok leads the team in a discussion regarding the technical strategy that they will take to implement it. Based on this “just-in-time” design, the team identifies its development and testing tasks in a similar way to the last iteration. At several points, Danny and Ashok work through an idea on the whiteboard while others provide input. Although this modeling proves to be of value, the team realizes that it adds time to their planning session.

Since the team is now more familiar with the process, the planning session goes a bit smoother than it did in the previous iteration. However, it takes longer than expected due to the need to work through the business logic and implementation details. This further reinforces their decision to start doing look-ahead modeling each iteration, one of the learnings identified in their retrospective from the last iteration. Terry volunteers to clean up the task board from the previous iteration and set up the board with the new work items and tasks. After lunch, the team is ready to jump in and start working on the items

Days 1–5. The team starts doing the work required to implement the stories, including the story they didn't complete in Iteration C1 that they've picked for this two-week iteration. Although everyone is sitting together in the agile pod, they are still working (for the most part) separately. Whenever someone runs into difficultly, such as how to specifically write a section of code, they ask someone else for help. Danny, Debbie, and Terry typically ask Ashok for help, as he has many years of development experience. Every so often, a team member asks Patricia or Barbara to do a bit of just-in-time (JIT) model storming with them to work through the details of some business logic or how a user interface feature should behave.

Dick continues to pair with other team members on database functionality when needed. He also continues to work on the detailed data model and pretty much finishes it this week.

Tara and Carlos work on getting the team's continuous integration (CI) strategy up and running. Carlos has done

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.